Date: Fri, 27 May 94 04:30:08 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: Bulk Subject: TCP-Group Digest V94 #101 To: tcp-group-digest TCP-Group Digest Fri, 27 May 94 Volume 94 : Issue 101 Today's Topics: Idea for nntp Lurker needs info Pacificon ARRL Pacific Division Convention Returned Mail RSPF questions Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Fri, 27 May 1994 00:22:43 -0600 From: ve6eei@ve6eei.ampr.ab.ca (Evan E. Idler, Edmonton, AB [192.75.200.5]) Subject: Idea for nntp To: tcp-group@UCSD.EDU, nos-bbs@hydra.carleton.ca I have a idea on how to improve the nntp in jnos, so that people can read messages a little easier, and expire them, without headackes. I'm not a programer, so this is out of my league, but somebody else might take it and make it work. The idea is to add an "NNTP DUMP-AND-DELETE" cammand. The command would do a controlled nntp dump, them after it dumps the message, it would delete it. There could be a control file in the /spool directory ie. nntpdump.txt that would tell the command which area's to dump, and to which mailbox to dump them. ie. rec/radio/amateur/digital/misc miscdgtl rec/radio/amateur/space space When the command is called it would dump all news articles in rec/radio/amateur/digital/misc into the "miscdgtl" mailbox, and all rec/radio/amateur/space articles into the "space" mailbox. It would also delete all the nntp articles that it has dumped, then update the news.rc file so that the normal nntp read command would still work it desired. This would also make it easier to read the different news adticles with your favorite mailer, instead of the cripled nos nntp reader. It would also let ax25 user read the nntp articles if desired, thru the standard nos bbs system, and you can use the normal nos expire command to kill the messages. You would also be able to call the dump-and-delete command with the "AT" command so that it would do it once every couple hours, or just add a time variable to the command so that it would fire up at a user defined interval. ie. nntp dump-and-delete 7200 for every two hours. What do you think of this idea. Anybody interested in adding this feature to jnos? 73 Evan ======================================================================= Evan E. Idler | Of All The Things I've Lost ve6eei@ve6eei.ampr.ab.ca | In Life, I Miss My MIND The Edmonton, Alberta, Canada | Most!!! Amateur Packet Radio Station VE6EEI [192.75.200.5] ======================================================================= ------------------------------ Date: Thu, 26 May 1994 21:23:27 -0800 (GMT-0800) From: John W Redelfs Subject: Lurker needs info To: tcp-group@UCSD.EDU Hi, I've been lurking for the last few weeks hoping to learn something about using packet radio on the Internet. Nearly all of the discussion is way over my head, though. I am a computer hobbiest, not a ham or radio hobbiest. Is there a FAQ for this group? Where could I get introductory information about packet radio Internetting? Either email or posts to the list directing me to other sources would be appreciated. Maybe there is a newsgroup on Usenet? John W. Redelfs, tsjwr@camelot.acf-lab.alaska.edu ------------------------------ Date: Thu, 26 May 94 16:29 PDT From: bruce@pixar.com (Bruce Perens) Subject: Pacificon ARRL Pacific Division Convention To: tcp-group@ucsd.edu This year at Pacificon there will be an "Intro to TCP/IP" session offered by NCPA (Northern California Packet Association). I am compiling a list of "TCP/IP Elmers" that will be given out to to the attendees of the TCP/IP program, and at the NCPA table. If you'd like to be a "TCP/IP Elmer", please reply with your name, callsign, town, and phone number. If you know them, include your grid square or coordinates as I'll be attempting a map. I'm also collecting a list of non-TCP packet "Elmers" as well. If you would like to talk about the way that NCPA is representing you, please call me during the day at 510-215-3502. I'm the first TCP/IP representative on NCPA's board and I want to make sure that they represent all aspects of packet radio. Thanks Bruce Perens AB6YM ------------------------------ Date: Thu, 26 May 94 11:19 CDT From: Postmaster@mail.admin.wisc.edu Subject: Returned Mail To: tcp-group@ucsd.edu Mail could not be delivered to the following recipients: JQB@ADP -------- Original Message Follows ------- X-ENVELOPE-FROM: X-TO: Received: from wingra.adp.wisc.edu by BLUE.ADP.WISC.EDU (IBM MVS SMTP V2R2.1) with TCP; Thu, 26 May 94 11:08:46 CST Received: from audumla.students.wisc.edu (students.wisc.edu) by wingra.adp.wisc.edu with SMTP id AA11534 (5.65c/IDA-1.5 for ); Thu, 26 May 1994 11:13:10 -0500 Received: from ›144.92.104.230| by audumla.students.wisc.edu; id LAA38570; 8.1C/42; Thu, 26 May 1994 11:08:46 -0500 Message-Id: <199405261608.LAA38570@audumla.students.wisc.edu> X-Sender: landmann@facstaff.wisc.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 May 1994 11:12:36 -0600 XT: jqb@mail.admin.wisc.edu, pat.davis@mail.admin.wisc.edu From: Advanced Amateur Radio Networking Group (by way of landmann@facstaff.wisc.edu (Thomas Landmann)) Subject: TCP-Group Digest V94 #100 TCP-Group Digest Wed, 25 May 94 Volume 94 : Issue 100 Today's Topics: Public Domain XNS/IDP Protocol Code? Returned Mail (2 msgs) Tango disk ??? Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Tue, 24 May 1994 12:34:29 -0400 (EDT) From: TROYGAU@delphi.com Subject: Public Domain XNS/IDP Protocol Code? To: tcp-group@ucsd.edu Can anyone tell me where to find the public domain XNS/IDP protocol code? I'll share the information once I receive enough inputs. Thank you. Shinjou Fang troygau@delphi.com ------------------------------ Date: Tue, 24 May 94 07:13 CDT From: Postmaster@mail.admin.wisc.edu Subject: Returned Mail To: tcp-group@UCSD.EDU Mail could not be delivered to the following recipients: RELAY.TCP-GROUP@ADP -------- Original Message Follows ------- X-ENVELOPE-FROM: X-TO: Received: from pgd.adp.wisc.edu by BLUE.ADP.WISC.EDU (IBM MVS SMTP V2R2.1) with TCP; Tue, 24 May 94 07:10:19 CST Received: from ucsd.edu by pgd.adp.wisc.edu with SMTP id AA17769 ; Mon, 23 May 94 10:08:27 CST Received: by ucsd.edu; id EAA05080 sendmail 8.6.9/UCSD-2.2-sun Sun, 22 May 1994 04:30:09 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA05075 sendmail 8.6.9/UCSD-2.2-sun Sun, 22 May 1994 04:30:06 -0700 for tcp-group-ddist Message-Id: <199405221130.EAA05075@ucsd.edu> Date: Sun, 22 May 94 04:30:04 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@ucsd.edu Reply-To: TCP-Group@ucsd.edu Precedence: Bulk Subject: TCP-Group Digest V94 #97 XT: tcp-group-digest@ucsd.edu TCP-Group Digest Sun, 22 May 94 Volume 94 : Issue 97 Today's Topics: Returned Mail Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sat, 21 May 94 08:42 CDT From: Postmaster@mail.admin.wisc.edu Subject: Returned Mail To: tcp-group@UCSD.EDU Mail could not be delivered to the following recipients: RELAY.TCP-GROUP@ADP -------- Original Message Follows ------- X-ENVELOPE-FROM: X-TO: Received: from pgd.adp.wisc.edu by BLUE.ADP.WISC.EDU (IBM MVS SMTP V2R2.1) with TCP; Sat, 21 May 94 08:39:48 CST Received: from ucsd.edu by pgd.adp.wisc.edu with SMTP id AA17671 ; Sat, 21 May 94 08:06:01 CST Received: by ucsd.edu; id EAA15049 sendmail 8.6.9/UCSD-2.2-sun Sat, 21 May 1994 04:30:07 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA15044 sendmail 8.6.9/UCSD-2.2-sun Sat, 21 May 1994 04:30:06 -0700 for tcp-group-ddist Message-Id: <199405211130.EAA15044@ucsd.edu> Date: Sat, 21 May 94 04:30:05 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Precedence: Bulk Subject: TCP-Group Digest V94 #96 XT: tcp-group-digest@UCSD.EDU TCP-Group Digest Sat, 21 May 94 Volume 94 : Issue 96 Today's Topics: Returned Mail subscribe unsubscribe Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Fri, 20 May 94 09:50 CDT From: Postmaster@mail.admin.wisc.edu Subject: Returned Mail To: tcp-group@UCSD.EDU Mail could not be delivered to the following recipients: RELAY.TCP-GROUP@ADP -------- Original Message Follows ------- X-ENVELOPE-FROM: X-TO: Received: from pgd.adp.wisc.edu by BLUE.ADP.WISC.EDU (IBM MVS SMTP V2R2.1) with TCP; Fri, 20 May 94 09:47:34 CST Received: from ucsd.edu by pgd.adp.wisc.edu with SMTP id AA17601 ; Fri, 20 May 94 09:21:53 CST Received: by ucsd.edu; id EAA24463 sendmail 8.6.9/UCSD-2.2-sun Fri, 20 May 1994 04:30:14 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA24448 sendmail 8.6.9/UCSD-2.2-sun Fri, 20 May 1994 04:30:11 -0700 for tcp-group-ddist Message-Id: <199405201130.EAA24448@ucsd.edu> Date: Fri, 20 May 94 04:30:08 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Precedence: Bulk Subject: TCP-Group Digest V94 #95 XT: tcp-group-digest@UCSD.EDU TCP-Group Digest Fri, 20 May 94 Volume 94 : Issue 95 Today's Topics: Returned Mail Unix version of convers? (2 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Thu, 19 May 94 08:31 CDT From: Postmaster@mail.admin.wisc.edu Subject: Returned Mail To: tcp-group@ucsd.edu Mail could not be delivered to the following recipients: RELAY.TCP-GROUP@ADP -------- Original Message Follows ------- X-ENVELOPE-FROM: X-TO: Received: from pgd.adp.wisc.edu by BLUE.ADP.WISC.EDU (IBM MVS SMTP V2R2.1) with TCP; Thu, 19 May 94 08:29:04 CST Received: from ucsd.edu by pgd.adp.wisc.edu with SMTP id AA17543 ; Thu, 19 May 94 07:40:46 CST Received: by ucsd.edu; id EAA16700 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:08 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA16686 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:07 -0700 for tcp-group-ddist Message-Id: <199405191130.EAA16686@ucsd.edu> Date: Thu, 19 May 94 04:30:05 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Precedence: Bulk Subject: TCP-Group Digest V94 #94 XT: tcp-group-digest@UCSD.EDU TCP-Group Digest Thu, 19 May 94 Volume 94 : Issue 94 Today's Topics: UNIVPERM Security Problem (2 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Wed, 18 May 94 14:40:25 CST From: rtorres@tazz.coacade.uv.mx Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu Hi Folks!!. I have a security problem with the univperm permission. When it is set, anyone can access any of the mailboxes by doing this: By example, your login is root, and password xxxx. Then someone can access your mailbox by entering 'rootxx', and any password he wants. Off course it can be easily resolved by verifying that the login does not contain a separator character before accepting it :), returning a 'wrong login' message or something so. What do you think?? Greetings!! Roman -=-=-=-=-=-=-=-= Roman Torres Programmer rtorres@tazz.coacade.uv.mx Tazz BBS MEXICO ------------------------------ Date: Wed, 18 May 94 17:32:18 HST From: tony@mpg.phys.hawaii.edu (Antonio Querubin) Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu, nos-bbs@hydra.carleton.ca > Hi Folks!!. I have a security problem with the univperm permission. When it is > set, anyone can access any of the mailboxes by doing this: By example, your > login is root, and password xxxx. Then someone can access your mailbox by > entering 'rootxx', and any password he wants. > Off course it can be easily resolved by verifying that the login does not > contain a separator character before accepting it :), returning a 'wrong login' > message or something so. What do you think?? Just put a 'root' entry into ftpusers with an obscure password. Do the same for any username that has to be secured... Tony ------------------------------ End of TCP-Group Digest V94 #94 ****************************** ------------------------------ Date: Thu, 19 May 94 09:41 PDT From: bob@nyssa.wa7ipx.ampr.org (Bob Finch) Subject: Unix version of convers? To: tcp-group@ucsd.edu Are there Unix implementations of convers servers that work with the JNOS convers server? Any pointers to source available by ftp would be appreciated. 73 -- Bob ------------------------------ Date: Thu, 19 May 94 13:12:15 MDT From: Dieter Deyke Subject: Unix version of convers? To: tcp-group@ucsd.edu > Are there Unix implementations of convers servers that work with the > JNOS convers server? > > Any pointers to source available by ftp would be appreciated. Check out WAMPES on UCSD.EDU. 73, -- Dieter Deyke - deyke@fc.hp.com - dk5sg@db0sao.ampr.org ------------------------------ Date: Thu May 19 13:12:56 GMT 1994 From: smtp@zeus.USG.Sandy.Novell.COM To: tcp-group@ucsd.edu >From smtp Thu May 19 07:12 MDT 1994 Received: from UCSD.EDU by mycroft.IS.Sandy.Novell.COM; Thu, 19 May 94 07:12 MDT Received: from ucsd.edu by ns.Novell.COM (4.1/SMI-4.1) id AA11128; Thu, 19 May 94 07:07:50 MDT Received: by ucsd.edu; id EAA16700 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:08 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA16686 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:07 -0700 for tcp-group-ddist Errors-To: TCP-Group-Errors@UCSD.EDU Message-Id: <199405191130.EAA16686@ucsd.edu> Date: Thu, 19 May 94 04:30:05 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Content-Length: 2414 Content-Type: text Precedence: Bulk Subject: TCP-Group Digest V94 #94 To: tcp-group-digest@UCSD.EDU TCP-Group Digest Thu, 19 May 94 Volume 94 : Issue 94 Today's Topics: UNIVPERM Security Problem (2 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Wed, 18 May 94 14:40:25 CST From: rtorres@tazz.coacade.uv.mx Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu Hi Folks!!. I have a security problem with the univperm permission. When it is set, anyone can access any of the mailboxes by doing this: By example, your login is root, and password xxxx. Then someone can access your mailbox by entering 'rootxx', and any password he wants. Off course it can be easily resolved by verifying that the login does not contain a separator character before accepting it :), returning a 'wrong login' message or something so. What do you think?? Greetings!! Roman -=-=-=-=-=-=-=-= Roman Torres Programmer rtorres@tazz.coacade.uv.mx Tazz BBS MEXICO ------------------------------ Date: Wed, 18 May 94 17:32:18 HST From: tony@mpg.phys.hawaii.edu (Antonio Querubin) Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu, nos-bbs@hydra.carleton.ca > Hi Folks!!. I have a security problem with the univperm permission. When it is > set, anyone can access any of the mailboxes by doing this: By example, your > login is root, and password xxxx. Then someone can access your mailbox by > entering 'rootxx', and any password he wants. > Off course it can be easily resolved by verifying that the login does not > contain a separator character before accepting it :), returning a 'wrong login' > message or something so. What do you think?? Just put a 'root' entry into ftpusers with an obscure password. Do the same for any username that has to be secured... Tony ------------------------------ End of TCP-Group Digest V94 #94 ****************************** ------------------------------ Date: Thu May 19 13:28:00 GMT 1994 From: smtp@zeus.USG.Sandy.Novell.COM To: tcp-group@ucsd.edu >From smtp Thu May 19 07:27 MDT 1994 Received: from UCSD.EDU by mycroft.IS.Sandy.Novell.COM; Thu, 19 May 94 07:27 MDT Received: from ucsd.edu by ns.Novell.COM (4.1/SMI-4.1) id AA11128; Thu, 19 May 94 07:07:50 MDT Received: by ucsd.edu; id EAA16700 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:08 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA16686 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:07 -0700 for tcp-group-ddist Errors-To: TCP-Group-Errors@UCSD.EDU Message-Id: <199405191130.EAA16686@ucsd.edu> Date: Thu, 19 May 94 04:30:05 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Content-Length: 2414 Content-Type: text Precedence: Bulk Subject: TCP-Group Digest V94 #94 To: tcp-group-digest@UCSD.EDU TCP-Group Digest Thu, 19 May 94 Volume 94 : Issue 94 Today's Topics: UNIVPERM Security Problem (2 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Wed, 18 May 94 14:40:25 CST From: rtorres@tazz.coacade.uv.mx Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu Hi Folks!!. I have a security problem with the univperm permission. When it is set, anyone can access any of the mailboxes by doing this: By example, your login is root, and password xxxx. Then someone can access your mailbox by entering 'rootxx', and any password he wants. Off course it can be easily resolved by verifying that the login does not contain a separator character before accepting it :), returning a 'wrong login' message or something so. What do you think?? Greetings!! Roman -=-=-=-=-=-=-=-= Roman Torres Programmer rtorres@tazz.coacade.uv.mx Tazz BBS MEXICO ------------------------------ Date: Wed, 18 May 94 17:32:18 HST From: tony@mpg.phys.hawaii.edu (Antonio Querubin) Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu, nos-bbs@hydra.carleton.ca > Hi Folks!!. I have a security problem with the univperm permission. When it is > set, anyone can access any of the mailboxes by doing this: By example, your > login is root, and password xxxx. Then someone can access your mailbox by > entering 'rootxx', and any password he wants. > Off course it can be easily resolved by verifying that the login does not > contain a separator character before accepting it :), returning a 'wrong login' > message or something so. What do you think?? Just put a 'root' entry into ftpusers with an obscure password. Do the same for any username that has to be secured... Tony ------------------------------ End of TCP-Group Digest V94 #94 ****************************** ------------------------------ Date: Thu May 19 13:52:17 GMT 1994 From: smtp@zeus.USG.Sandy.Novell.COM To: tcp-group@ucsd.edu >From smtp Thu May 19 07:52 MDT 1994 Received: from UCSD.EDU by mycroft.IS.Sandy.Novell.COM; Thu, 19 May 94 07:52 MDT Received: from ucsd.edu by ns.Novell.COM (4.1/SMI-4.1) id AA11128; Thu, 19 May 94 07:07:50 MDT Received: by ucsd.edu; id EAA16700 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:08 -0700 for tcp-digest-list Received: by ucsd.edu; id EAA16686 sendmail 8.6.9/UCSD-2.2-sun Thu, 19 May 1994 04:30:07 -0700 for tcp-group-ddist Errors-To: TCP-Group-Errors@UCSD.EDU Message-Id: <199405191130.EAA16686@ucsd.edu> Date: Thu, 19 May 94 04:30:05 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.EDU Reply-To: TCP-Group@UCSD.EDU Content-Length: 2414 Content-Type: text Precedence: Bulk Subject: TCP-Group Digest V94 #94 To: tcp-group-digest@UCSD.EDU TCP-Group Digest Thu, 19 May 94 Volume 94 : Issue 94 Today's Topics: UNIVPERM Security Problem (2 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Wed, 18 May 94 14:40:25 CST From: rtorres@tazz.coacade.uv.mx Subject: UNIVPERM Security Problem To: tcpgroup@ucsd.edu Hi Folks!!. I have a security problem with the univperm permission. When it is set, anyone can access any of the mailboxes by doing this: By example, your login is root, and password xxxx. Then someone can access your mailbox by entering 'rootxx', and any password he wants. Off course it can be easily resolved by verifying that the login does not contain a separator character before accepting it :), returning a 'wrong login' message or something so. What do you think?? Greetings!! Roman -=-=-=-=-=-=-=-= Roman Torres Programmer rtorres@tazz.coacade.uv.mx Tazz BBS MEXICO ------------------------------ Date: Wed, 18 May 94 17:32:18 HST From: tony@mpg.phys.hawaii.edu (Antonio Querubin) Subject: UNIVPERM Security Problem ------------------------------ Date: Thu, 26 May 94 06:44:48 CST From: Jack Snodgrass Subject: RSPF questions To: tcp-group mailling list I've started running RSPF to see how well it handles dynamic routing in our network. I've got a couple of questions that I hope someone who's running RSPF can help answer. First of all... I have the unique broadcast addresses for each port/freq. Are all the broadcast addresses supposed to be the same or just the same on each port/freq? If I have a sub-net route ( 44.28.1/24 ) set up to a router box, why would RSPF add unique, 32-bit address routes for everyone in the sub-net. I.E. I have route add 44.28.1/24 enet router.kf5mg metric 1 when I start and after a bit, I end up with add 44.28.1/24 enet router.kf5mg metric 1 add 44.28.1.1 enet router.kf5mg metric 16 add 44.28.1.2 enet router.kf5mg metric 16 add 44.28.1.3 enet router.kf5mg metric 16 add 44.28.1.4 enet router.kf5mg metric 16 add 44.28.1.5 enet router.kf5mg metric 16 I assume that when I broadcast my 'Hey... I can hear the following stations...' I'm going to list all the new routes that RSPF has added to my routing table even if they are covered by the sub-net route. RSPF pings local stations and records the results. Where does it get the Initial list of stations to ping? Does RSPF only handle stations you can hear directly? If so..., what about a station that you have a route to that goes via a station ( x1j node ) that doesn't do RSPF. How can you get a station like that in your RSPF tables? I have 2 Internet Gateways. One gateway has 3 RF ports and the other gateway has 1 RF port. The gateways talk to each other over an Internet Link. How do I get the two gateway to talk RSPF to each other? They are not on the same network so they won't hear each others RSPF broadcast. Both gateways are part of our local network, so it's imperative that they talk RSPF to each other. Guess that's about it. I'm running the RSPF code that's in JNOS 1.10b. If there's a later-and-greater-but-not-in-jnos-1.10b version of RSPF, please let me know. Thanks. 73's de Jack - kf5mg Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14 AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386 Dialup - kf5mg@tcet.unt.edu - work (looking for) =============================================================================== === Buffalo's new area code.... 044.... "Deal with it" === =============================================================================== ------------------------------ End of TCP-Group Digest V94 #101 ******************************